Enable pyink on tests, fix VSCode pyink config to avoid bad Python version. #47
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
danieldjohnson
force-pushed
the
fix_pyink
branch
4 times, most recently
from
dd9e7ce to
5106763
Compare
Turns on checking pyink formatting for test files. Also disables a bad Python version for pyink: Black and Pyink do not support python 3.12.5, but uvx automatically selects this version occasionally, which breaks autoformatting in VSCode. Also fixes remaining lint issues.
danieldjohnson
force-pushed
the
fix_pyink
branch
from
5106763 to
d3db2ee
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Turns on checking pyink formatting for test files.
Also disables a bad Python version for pyink.
Black and Pyink do not support python 3.12.5, but uvx automatically selects this version occasionally, which breaks autoformatting in VSCode.